Systems and methods for determining data dependency for dynamic tiles

ABSTRACT

A system and method to dynamically update a data field are disclosed. In some embodiments, data may be received from a plurality of databases and organized into a plurality of data fields. A first data field may be associated with a single database of the plurality of databases. A user may modify the first data field and the system and method may identify a dependency between the first data field and at least a second data field. The second data field may be updated based on the dependency between the first data field and the second data field.

FIELD

The present disclosure relates to systems and methods for datadependency. In some embodiments, the present disclosure relates tosystems and methods for determining data dependency for dynamic tiles.

BACKGROUND

Conventional user interfaces for a user platform (e.g., an applicationprogram) using a database or an aggregate of databases are typicallystatic. The conventional user platform may receive data from one or moreexternal databases. For example, the conventional user platform mayquery a plurality of databases and organize data from the querieddatabases into the database of the user platform. As such, the userinterface of the conventional user platform may display data fieldscomprising information or data queried from a plurality of databases.

Conventional user platforms do not dynamically respond to a change to adata field. As such, conventional user platforms tend to be static. Forexample, if a user changes a data field in a user interface of the userplatform, then other data fields associated with the changed data fieldmay be out of date or incorrect.

As such, it is desirable to develop systems and methods of systems andmethods for implementing a dynamic data platform associated with aplurality of databases. For example, systems and methods for determiningdata dependency for dynamic tiles may address such functionality.

SUMMARY

The present disclosure introduces systems and methods for determiningdata dependency for dynamic tiles.

The systems or methods may receive data from a plurality of databases.The received data may be organized into a plurality of data fields. Insome embodiments, a first data field is associated with a singledatabase of the plurality of databases. The system or method may furtherreceive a modification to the first data field of the plurality of datafields and identify a dependency between the first data field and otherdata fields of the plurality of data fields. Furthermore, the systems ormethods may update a second data field of the plurality of data fieldsbased on the dependency between the first data field and the other datafields. In some embodiments, the second data field is updated if thesecond data field is dependent upon the first data field.

In some embodiments, the dependency between the first data field and theother data fields of the plurality of data fields comprises anindication that a modification to the first data field requires anupdating of at least one data field of the other data fields.

In some embodiments, the systems or methods may further display aplurality of dynamic tiles based on a user selection of a first entry.In the same or alternative embodiments, a first dynamic tile comprisesat least one of the data fields and is associated with a first query.The systems or methods may further receive a user selection of a secondentry and execute the first query associated with the first dynamic tilein response to the user selection.

In some embodiments, the execution of the first query is performedwithout a user input of query keywords. The systems or methods mayfurther display the first dynamic tile with at least one updated datafield in response to the execution of the first query. In someembodiments, the at least one updated data field is at least partlybased on the user selection of the second entry

In some embodiments, the first data field is associated with a firstdatabase and the second data field is associated with a second database,the updating of the second data field results in the querying of thesecond database based on the modification of the first data field.

In some embodiments, the first database and the second database areindependent of each other such that the first database and the seconddatabase are associated with different locations and differentadministrators.

In some embodiments, the systems or methods are to facilitate an importor export compliance environment.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the disclosure are set forth in the appendedclaims. However, for purpose of explanation, several embodiments of thedisclosure are set forth in the following figures.

FIG. 1 is a block diagram of an example import and export complianceenvironment in accordance with some embodiments.

FIG. 2 is a block diagram of an example environment for a system and/ormethod for determining data dependency for dynamic tiles.

FIG. 3 is a flow diagram of an example method for determining datadependency for dynamic tiles in accordance with some embodiments.

FIG. 4 depicts an example data table comprising data fields inaccordance with some embodiments of the present disclosure.

FIG. 5 is a block diagram of an example environment using a data enginefor determining data dependence for dynamic tiles.

FIG. 6 is a flow diagram illustrating an example method for using datadependencies to query one or more databases in response to a change of adata field in accordance with some embodiments.

FIG. 7 depicts an example user interface comprising dynamic tiles inaccordance with some embodiments.

FIG. 8 depicts a diagram illustrating an exemplary computing system forexecution of the operations comprising various embodiments of thedisclosure.

FIG. 9 depicts an example dynamic data platform system for determiningdata dependency of dynamic tiles.

DETAILED DESCRIPTION

The systems and methods disclosed herein relate to determining datadependency for dynamic tiles.

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of the presentdisclosure. However, it will become obvious to those skilled in the artthat the present disclosure may be practiced without these specificdetails. The description and representation herein are the common meansused by those experienced or skilled in the art to most effectivelyconvey the substance of their work to others skilled in the art. Inother instances, well known methods, procedures, and systems have notbeen described in detail to avoid unnecessarily obscuring aspects of thepresent disclosure.

FIG. 1 is a block diagram of an example import and export complianceenvironment 100 in accordance with some embodiments. In general, theenvironment 100 may comprise a plurality of locations and a plurality oftransactions associated with the trade of products between a pluralityof entities.

As shown in FIG. 1, the environment 100 may comprise locations 110, 120,and 130. Each of the locations may correspond to the source ordestination associated with the shipment and/or receiving of a product.For example, the location 110 may be associated with the origination orsource of a product and a transaction 115 may comprise the shipment ofthe product from the location 110 to the location 120. As such, thelocation 120 may comprise the destination associated with thetransaction 115. In some embodiments, the transaction 115 may beassociated with one or more entities. For example, the transaction 115may be associated with a vendor (e.g., a supplier or manufacturer of theproduct), broker, customer, etc. As such, a vendor of the product at thelocation 110 may ship a product to a broker at the location 120 as thetransaction 115. In some embodiments, the location 120 may also be thesource for a transaction 125. For example, an entity associated with thedestination of transaction 115 may further ship the product to anotherentity at a location 130. As such, the transaction of a product from thelocation 110 to a final destination at location 130 may comprise aplurality of transactions (e.g., sub-transactions) 115 and 125 and aplurality of entities (e.g., a shipper at location 110, a receiver andshipper at location 120, a receiver at location 130, etc.).

In some embodiments, each of the transactions 115 and 125 to ship aproduct from the location 110 to the location 130 may require importand/or export compliance information. For example, information regardingthe product being shipped, shipping information, customs information,and other import and export compliance information may need to be keptand/or sent to other entities. Furthermore, in some embodiments, each ofthe locations 110, 120, and 130 may be associated with a plurality ofdatabases. For example, location 110 may be associated with databases111 and 112, location 120 may be associated with databases 121 and 122,and location 130 may be associated with databases 131 and 132. In someembodiments, the databases may correspond to location specificinformation. For example, a database may comprise Harmonized TariffSchedule (HTS) codes for a particular country, product cataloginformation of a shipper or receiver, or any other database comprisinginformation necessary for completing a transaction.

As is evident from the above discussion, a transaction of a product maybe associated with a plurality of sub-transactions, entities, locations,and databases. Organizing such information and facilitating access tothe information for entities in the transaction chain of the environment100 may require a coordinated and complicated workflow. Systems andmethods to facilitate the workflow of the environment 100 are discussedin further detail below. For example, a user platform that determinesdata dependencies for dynamic tiles may address the above issues.Furthermore, the user platform may aggregate data from widely dispersedand independent sources (e.g., databases 111, 112, 121, 122, 131, and132) to facilitate a highly distributed transactional-based workflowmanagement.

FIG. 2 is a block diagram of an example environment 200 for a systemand/or a method for determining data dependency for dynamic tiles. Ingeneral, the environment 200 may comprise a user interface fororganizing and displaying data from one or more databases.

As shown in FIG. 2, the environment 200 may comprise a plurality ofdatabases (e.g., database 210, database 220, and database 230). In someembodiments, each of the databases 210, 220, and/or 230 may beindependent of each other. For example, each of the databases 210, 220,and/or 230 may be associated with a separate administrative entityand/or a different location. In some embodiments, each of the locationsmay be associated with a different firewall and/or network. For example,each of the databases 210, 220, and/or 230 may be on a separate networkand behind a separate firewall. The databases 210, 220, and/or 230 mayfurther be based on and/or operated by different platforms (e.g.,software applications, software operating systems, etc.). Thus, each ofthe databases 210, 220, and/or 230 may be associated with a differententity at different locations (e.g., network locations) where each ofthe locations comprises a different firewall and a different platformfor operating the databases 210, 220, and/or 230. In some embodiments,the entities associated with the databases 210, 220, and/or 230 may notaccess each of the other databases. For example, each of the databases210, 220, and/or 230 may operate without knowing of or connecting withany of the other databases 210, 220, and/or 230. As such, each databaseof the environment 200 may be considered independent of each of theother databases of the environment 200 and the databases may further beconsidered widely dispersed databases. For example, database 210 may bea database associated with a governmental entity, database 220 may be adatabase associated with an enterprise software systems of a firstcorporation, and database 230 may be a database associated with anenterprise software systems of a second corporation. In someembodiments, a network 240 (e.g., the Internet) may communicativelycouple each of the databases 210, 220, and 230 to a user platform 250.In some embodiments, the user platform 250 may comprise data groups 260,270, and 280. The user platform 250 may query one or more of thedatabases 210, 220, and/or 230 to request data from the one or moredatabases. For example, the user platform 250 may transmit a query toreceive data from each of the databases 210, 220, and 230 over thenetwork 240. In response, each of the databases 210, 220, and 230 maytransmit data associated with the query from the user platform 250 overthe network 240 to the user platform 250. In some embodiments, the userplatform 250 may organize or structure the data received from thedatabases 210, 220, and 230. For example, the user platform 250 mayplace the received data from database 210 into the data group 260, thereceived data from database 220 into the data group 270, and thereceived data from the database 230 into the data group 280. As such,the user platform 250 may be aware of where a specific received andstored data originates from among the databases 210, 220, and 230. Insome embodiments, the data from the databases 210, 220, and 230 may beorganized by the user platform 250 into dynamic tiles. Furthermore, datadependencies from the received data from the database 210, 220, and 230may be identified. Further details with regard to such organization ofdata into dynamic tiles and identification of data dependencies arediscussed in further detail below.

FIG. 3 is a flow diagram of an example method 300 for determining datadependencies for dynamic tiles in accordance with some embodiments. Ingeneral, the method 300 may update a data field in response to amodification of a data field by using data dependencies associated withthe modified data field.

As shown in FIG. 3, at step 310, the method 300 may receive data fromone or more databases. For example, a user platform (e.g., user platform250) may request data from one or more databases (e.g., databases 210,220, and/or 230) and receive the requested data over a network (e.g.,network 240). Next, at step 320, data dependencies may be determined oridentified. For example, a user platform (e.g., user platform 250) maydetermine or identify data dependencies from the data received from theone or more databases. In some embodiments, data dependency maycorrespond to a first data needing to be updated or a database fromwhich the data originates needing to be queried in response to amodification of a second data. As such, the user platform may identifywhether all or a portion of the data received from a first database(e.g., database 210) is dependent upon data received from a seconddatabase (e.g., database 220) or a third database (e.g., database 230).Further details with regard to data dependency are discussed in furtherdetail below.

As shown in FIG. 3, at step 330, a change or modification of a datafield may be received. For example, a user platform (e.g., user platform250) may receive a notification that a data field has been modified. Insome embodiments, the modification of the data field may be from a userutilizing a user interface of the user platform or from a change to datastored on the database 210, 220, and/or 230. For example, a user maymanually modify a data field by utilizing the user interface of the userplatform or an administrator or other user of the database 210, 220,and/or 230 may modify data stored on the database and the user platformmay receive a notification or identify that such data has been modified(e.g., after querying the database). In some embodiments, a modificationto a data field may result in the user platform to verify or check datafields that are dependent upon the modified data field. At step 340,data fields may be dynamically updated based on the data dependencies.For example, a user platform (e.g., user platform 250) may update datafields in response to a modified data field. In some embodiments, theupdated data fields correspond to dependent data fields of the modifieddata field.

As such, data from one or more databases may be received. In someembodiments, the data may be organized into dynamic tiles, as furtherdiscussed below. In the same or alternative embodiments, the data may bedisplayed in data fields. Data dependencies between data fields may bedetermined. In some embodiments, a modification to a data field mayresult in the dynamic updating of a second data field if the second datafield is dependent upon the modified data field.

FIG. 4 depicts an example data table 400 comprising data fields inaccordance with some embodiments of the present disclosure. In general,the data table 400 may comprise a plurality of entries, each entrycomprising a plurality of data fields. In some embodiments, a userplatform (e.g., user platform 250) may comprise or use the data table400.

As shown in FIG. 4, the data table 400 may comprise a plurality of dataentries 405. In some embodiments, each of the data entries 405 mayfurther comprise data fields corresponding to a plurality of types ofdata. For example, each data entry 405 may comprise data correspondingto data columns 431, 432, 433, 434, 435, and 436. In some embodiments,each of the data entries 405 may correspond to an item relating toimport and/or export compliance. However, the example as shown in FIG. 4is merely for exemplary purposes and is not intended to be limited tothe data or types of data as show with regard to data columns 431, 432,433, 434, 435, and/or 436. Furthermore, the example as shown in FIG. 4is not intended to be limited to import and/or export complianceworkflows as such an example is for illustrative purposes. As such, adata table comprising data entries, some of which may be data dependent,may be used for other types of workflows outside of the scope or use ofimport and/or export compliance.

As shown in FIG. 4, the data column 431 may comprise data identifying adata entry reference identification, data column 432 may comprise datacorresponding to a sender, data column 432 may comprise datacorresponding to a receiver, data column 434 may comprise datacorresponding to a destination, data column 435 may comprise datacorresponding to a product, and data column 436 may comprise datacorresponding to a product code. As such, the data table 400 comprises aplurality of entries where each of the entries comprises a plurality ofdata fields. In some embodiments, a user platform (e.g., user platform250) may organize data received from a plurality of databases (e.g.,databases 210, 220, and/or 230) into the data table 400. For example,the data columns 432, 433, 434, and/or 435 may be associated with afirst database (e.g., data received from database 210) and the datacolumn 436 may be associated with a second database (e.g., data receivedfrom database 220). As such, the data table 400 may represent datareceived from a plurality of databases. In some embodiments, the userplatform may determine data dependencies of the data fields of the datatable 400. For example, the user platform may determine that the datafields from data column 432 and the data fields from the data column 433are not dependent upon each other. For example, the user platform maydetermine that the data field 410 and the data field 411 are independentof each other such that a change or modification of the data field 410does not need to result in the updating or querying with respect to datafield 411. In the same or alternative embodiments, the user platform maydetermine that the data fields from the data column 435 and the datafields from the data column 436 are dependent upon each other. Forexample, the user platform may determine that data field 420 and datafield 421 are dependent upon each other. In some embodiments, thedependency of data fields may be that if one of the data fields has beenmodified, then the modification may necessitate the updating and/orquerying of information of the second (e.g., not modified) data field.For example, as illustrated, a change of a product from the data field420 may result in the change of a product code from data field 436. Assuch, if a user or system modifies the data field 420, then the datafield 421 may automatically be updated in response to the modificationof the data field 420.

FIG. 5 is a block diagram of an example environment 500 using a dataengine for determining data dependencies for dynamic tiles. In general,the data engine of the environment 500 may determine and dynamicallymanage data fields based on data dependencies between the data fields.

As shown in FIG. 5, the environment 500 may comprise a plurality ofdatabases. For example, the environment 500 may comprise a database 210,database 220, and database 230. In some embodiments, each of thedatabases may be independent. For example, each database may beadministered by a separate entity. Furthermore, the database 210,database 220, and database 230 may be communicatively coupled to a dataengine 510 by a network 240. In some embodiments, a user platform (e.g.,user platform 250) may comprise the data engine 510. In the same oralternative embodiments, the data engine 510 may determine or identifydata dependencies from data received from the database 210, database220, and database 230. For example, the data engine 510 may receive aninput from a user that some portion or all of the data from a firstdatabase may be associated with or dependent upon another portion or allof the data from a second database. In the same or alternativeembodiments, the data engine 510 may further retrieve data from thedatabases 210, 220, and 230. For example, the databases may transmitdata to the data engine 510 (e.g., as illustrated from path 530). Thedata engine 510 may then organize the received data from the databases210, 220, and 230 (e.g., based on a schema using table 400). Forexample, the data engine 510 may organize the received data into aplurality of data fields. In some embodiments, each of the data fieldsmay comprise data received from a single database 210, 220, or 230. Assuch, the data engine 510 may indicate dependency between the datafields. For example, the data engine 510 may indicate data dependenciesof the data fields of the data table 400 and dynamically update the datafields of the data table 400 based on the data dependencies when a datafield is modified.

In some embodiments, the data engine 510 may be associated withpermission (e.g., access or update permission) to update one or more ofthe databases 210, 220, and 230. For example, the path 520 may beassociated with transmitting data from the database 210 to the dataengine 510, where the data may populate at least one of the data fieldsof the data table 400. In some embodiments, the data engine may modify(e.g., in response to a user input) one of the data fields where thedata from the database 210 has been populated. As such, the data engine510 may transmit the data from the modified data field to the database210 so that the database 210 may be updated to reflect the modifieddata.

FIG. 6 is a flow diagram illustrating an example method 600 for usingdata dependencies to query one or more databases in response to a changeof a data field in accordance with some embodiments. In general, themethod 600 may be used to dynamically update one or more data fields inresponse to a modification of another data field. In some embodiments, adata engine (e.g., data engine 510) may perform one or more of the stepsof the method 600.

As shown in FIG. 6, the method 600 may receive, at step 610, data fromone or more databases. For example, the data engine may receive datafrom a plurality of databases (e.g., database 210, 220, and/or 230). Atstep 620, the receive data may be organized into data fields in dynamictiles. For example, the data may be organized into a plurality of datafields where each data field is associated with data from a singledatabase. Further details with regard to the organization of the datainto dynamic tiles are further discussed below in association with FIG.7. At step 630, a modification to a data field may be received. Forexample, a modification or change to a data field of a dynamic tile maybe received from a user. Furthermore, at step 640, data fields that aredependent upon the modified data field may be identified. For example, adata engine (e.g., data engine 510) may identify or have previouslyidentified or received information to indicate which data fields aredependent with other data fields. As such, the data engine may determineor identify the data fields that are dependent upon the data field thathas been modified. Thus, the specific one or more data fields from aplurality of data fields that are associated or dependent upon themodified data field are identified. At step 650, databases that areassociated with the dependent data fields (e.g., data fields that aredependent or associated with the modified data field) may be queried.For example, databases (e.g., databases 210, 220, and/or 230) may bequeried if a data field is populated with data originally from thedatabase (e.g., data transmitted from the database to the data engineand/or user platform in response to a query). In some embodiments, eachdata field may be associated with a single database. As such, if aplurality of data fields is dependent or associated with the modifieddata field, then a plurality of databases may be queried in response tothe modification of the data field. For example, in some embodiments, afirst data field may be modified. In the same or alternativeembodiments, the first data field may be associated with a second datafield and a third data field. In some embodiments, the modification ofthe first data field may necessitate the updating of data of the seconddata field and the third data field (e.g., the second data field and thethird data field are dependent upon the first data field). Furthermore,the second data field may be associated with a first database (e.g., thesecond data field was originally populated with data retrieved from thefirst database) and the third data field may be associated with a seconddatabase (e.g., the third data field was originally populated with dataretrieved from the second database). As such, in order to update thesecond data field and the third data field in response to themodification of the first data field, the first database and the seconddatabase may need to be queried. For example, the first database may bequeried to retrieve new data for the second data field and the seconddatabase may be queried to retrieve new data for the third data field.In some embodiments, the querying of the first database and the seconddatabase may be based on the modification of the first data field and/orthe type of data comprised within the second data field and/or thirddata field. For example, in some embodiments, a product field maycomprise an identification of a first product. If the product data fieldis changed or modified (e.g., a user changes the product data field toindicate a second product instead of the first product), then dependentdata fields, such as a product code data field and a product supplierdata field, may be need to be updated in response to the modification ofthe product data field from an identification of the first product to anidentification of the second product as the product code and the productsupplier for the second product may differ from the product code and theproduct supplier of the first product. In some embodiments, the productcode data field may be associated with a product code database and theproduct supplier data field may be associated with a product supplierdatabase. In the same or alternative embodiments, each of the productcode database and the product supplier database may be administered bydistinct or separate entities. For example, each of the product codedatabase and the product supplier database may be associated with adifferent administrator, be associated with different permissions, andcomprise different locations (e.g., network locations). As such, inresponse to the modifying of the product data field, a plurality ofdatabases may be queried. Furthermore, the querying of each of thedatabases may be dependent upon the modification of the product datafield and the dependent data field. For example, the query for theproduct code database may request a new product code for the secondproduct (e.g., as indicated in the product data field) and a query forthe product supplier database may request a new product supplier for thesecond product. Moreover, at step 660, the method 600 may update thedependent data fields of dynamic tiles with the data received from thequery of step 650. For example, dependent data fields may be updated toreflect the change of a modified data field.

FIG. 7 depicts an example user interface 700 comprising dynamic tiles inaccordance with some embodiments. In general, the user interface 700 maycomprise a plurality of dynamic tiles for displaying information from aplurality of disparate sources (e.g., databases 210, 220, and/or 230)and information from a plurality of entities to facilitate a transaction(e.g., transactions 115 and 125). Furthermore, the user interface 700may comprise an online application (including data engine 510) that runswithin a web browser and capable of being accessed over a network (e.g.,network 240) by one or more entities or users.

As shown in FIG. 7, the user interface 700 may comprise a selection tile710 allowing a user (e.g., an entity as previously discussed) to selectone or more products. For example, the selection tile 710 may compriseentries 711, 712, and 713. In the example provided, the user interface700 corresponds to a selection of a product. However, the user interface700 may be used for other purposes and the example of a product andproduct information is merely provided as an example. In someembodiments, each of the entries 711, 712, and 713 corresponds to asingle product. For example, entry 711 is a ‘Grapple Camera Tripod.’ Theentry 711 displays a plurality of entry fields comprising informationrelating to the product. Furthermore, in some embodiments, the selectionof the entry 711 enables the display of a plurality of dynamic tiles.For example, if a user clicks on the entry 711, the user interface 700may display dynamic tiles 715, 720, 730, 735, 740, 745, 750, 760, and/or770. In some embodiments, each of the dynamic tiles comprises one ormore data fields that display information from one or more databases. Assuch, the organization of data from widely dispersed databases, aspreviously discussed, may be based on the use of the dynamic tiles ofthe user interface 700. In some embodiments, the dynamic tile 715 maycomprise product identifier data fields (e.g., product title, productSKU number, product family, manufacturer, product description, userplatform identification), the dynamic tile 720 may comprise productparts data fields, the dynamic tile 730 may comprise manufacturer datafields (e.g., identification of the manufacturer, country of origin,suppliers of the product), and the dynamic tile 735 may comprise datafields regarding the dimensions (e.g., unit of measurement, shippingweight, length, width, height, etc.) of the product (e.g., the ‘GrappleCamera Tripod’). In some embodiments, a dynamic tile 740 may compriseHTS codes for a plurality of countries for the product, the dynamic tile745 may comprise data fields for Export Control Classification Number(ECCN) codes for one or more countries, dynamic tile 750 may comprisedata fields for pricing information, dynamic tile 760 may comprise datafields for import licenses associated with the product, and dynamic tile770 may comprise data fields for export licenses associated with theproduct. Although specific types of dynamic tiles are disclosed above,any type of information may be organized into the data fields of thedynamic tiles.

In some embodiments, the selection of a different entry (e.g., entry 712and/or 713) may result in the dynamic changing of the dynamic tiles. Forexample, if a user has selected entry 711, the dynamic tiles may displaydata fields associated with the product of entry 711. However, if theuser clicks on the entry 712, the dynamic tiles may automatically updateto reflect the data fields associated with the product of entry 712. Insome embodiments, the updating may be performed on the same page withoutany reloading. For example, the clicking on the entries 711, 712, or 713may be enabled such that a webpage comprising the user interface 700does not reload in response to each click of an entry. Instead, thedynamic tiles may be updated immediately on the user interface on thewebpage without reloading the webpage. Furthermore, the clicking fromone entry to another in the user interface 700 may result in the dynamicquerying of one or more databases. For example, if a user clicks onentry 711, a plurality of databases may be queried for informationregarding the product of the entry 711. Received information may beorganized into the data fields of the dynamic tiles. Next, if a userclicks on the entry 713, the plurality of databases may be queried againfor information regarding the product of the entry 713. The newinformation regarding the product of the entry 713 may also be organizedinto the data fields of the dynamic tiles.

Furthermore, a user may update or modify the dynamic tiles. For example,the user may modify a data field of the dynamic tiles of the userinterface 700. In some embodiments, the modification of one of the datafields of a dynamic tile of the user interface 700 may be associatedwith the method 300 of FIG. 3 and the method 600 of FIG. 6.

In some embodiments, the dynamic tiles as shown in FIG. 7 may eachdisplay a portion of a database associated with the user interface 700.For example, each of the dynamic tiles of the user interface 700 maydisplay one or more data fields that have been received and organizedfrom a plurality of databases (e.g., database 210, 220, and/or 230 asdisclosed with relation to step 620 of FIG. 6, etc.). In someembodiments, each of the dynamic tiles may be associated with a query.For example, the dynamic tile 715 may be associated with a first queryfor the database associated with the user interface 700 and the dynamictile 720 may be associated with a second query for the databaseassociated with the user interface 700. In some embodiments, the queriesfor each of the dynamic tiles are a query for the data associated withthe data fields of the dynamic tiles. For example, the query for dynamictile 715 may request data associated with data fields for the producttitle, product SKU number, manufacturer, and user platform ID and thequery for dynamic tile 720 may request data associated with the datafield for HTS codes. In some embodiments, the queries for the dynamictiles are executed or run whenever a data field of the user interface700 (e.g., a data field displayed by a dynamic tile) is modified or aselection is made (e.g., a selection of entry 711, 712, and/or 713) inthe user interface 700. As such, the dynamic tiles may respond to anychange or input to the user interface 700. In some embodiments, thedynamic tiles may automatically update (e.g., reflect new data in thedata fields) without refreshing a webpage comprising the user interface700.

As such, an application program (e.g., an Internet application executingthe user interface 700 on a webpage) may determine data dependency fordynamic tiles. In some embodiments, the data dependency of data fieldsmay result in the execution of queries to external (e.g., widelydispersed) databases in response to a modification of a data field.Furthermore, the dynamic tiles may each be associated with a view ofparticular data of a database comprising organized information from aplurality of external databases. In some embodiments, the dynamic tilesmay execute a query to the database in response to a change or userselection of a data field or entry of the user interface 700. As such, auser does not have to input a query as the dynamic tiles mayautomatically execute a query in response to the change of a data fieldor the user selection of an entry.

The above disclosure may facilitate a plurality of transactional-basedenvironments. For example, although the above disclosure generallyrelates to import and export compliance, the user interfaces, methods,and systems may also be used to facilitate other suchtransactional-based workflows such as a healthcare workflow (e.g., aplurality of doctors and an insurance adjuster facilitating atransaction involving a patient).

FIG. 8 depicts a diagram illustrating a network 800 for execution of theoperations comprising various embodiments of the disclosure. Thediagrammatic representation of the network 800, including nodes forclient computer systems 802 ₁ through 802 _(N), nodes for servercomputer systems 804 ₁ through 804 _(N), nodes for networkinfrastructure 806 ₁ through 806 _(N), any of which nodes may comprise amachine 850 within which a set of instructions for causing the machineto perform any one of the techniques discussed above may be executed.The embodiment shown is purely exemplary, and might be implemented inthe context of one or more of the figures herein.

Any node of the network 800 may comprise a general-purpose processor, adigital signal processor (DSP), an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA) or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof capable to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices(e.g. a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration, etc.).

In alternative embodiments, a node may comprise a machine in the form ofa virtual machine (VM), a virtual server, a virtual client, a virtualdesktop, a virtual volume, a network router, a network switch, a networkbridge, a personal digital assistant (PDA), a cellular telephone, a webappliance, or any machine capable of executing a sequence ofinstructions that specify actions to be taken by that machine. Any nodeof the network may communicate cooperatively with another node on thenetwork. In some embodiments, any node of the network may communicatecooperatively with every other node of the network. Further, any node orgroup of nodes on the network may comprise one or more computer systems(e.g. a client computer system, a server computer system) and/or maycomprise one or more embedded computer systems, a massively parallelcomputer system, and/or a cloud computer system.

The computer system 850 includes a processor 808 (e.g. a processor core,a microprocessor, a computing device, etc.), a main memory 810 and astatic memory 812, which communicate with each other via a bus 814. Themachine 850 may further include a display unit 816 that may comprise atouch-screen, or a liquid crystal display (LCD), or a light emittingdiode (LED) display, or a cathode ray tube (CRT). As shown, the computersystem 850 also includes a human input/output (I/O) device 818 (e.g., akeyboard, an alphanumeric keypad, etc.), a pointing device 820 (e.g., amouse, a touch screen, etc.), a drive unit 822 (e.g. a disk drive unit,a CD/DVD drive, a tangible computer readable removable media drive, anSSD storage device, etc.), a signal generation device 828 (e.g. aspeaker, an audio output, etc.), and a network interface device 830(e.g. an Ethernet interface, a wired network interface, a wirelessnetwork interface, a propagated signal interface, etc.).

The drive unit 822 includes a machine-readable medium 824 on which isstored a set of instructions (i.e. software, firmware, middleware, etc.)826 embodying any one, or all, of the methodologies described above. Theset of instructions 826 is also shown to reside, completely or at leastpartially, within the main memory 810 and/or within the processor 808.The set of instructions 826 may further be transmitted or received viathe network interface device 830 over the network bus 814.

It is to be understood that embodiments of this disclosure may be usedas, or to support, a set of instructions executed upon some form ofprocessing core (such as the CPU of a computer) or otherwise implementedor realized upon or within a machine- or computer-readable medium. Amachine-readable medium includes any mechanism for storing informationin a form readable by a machine (e.g. a computer). For example, amachine-readable medium includes read-only memory (ROM); random accessmemory (RAM); magnetic disk storage media; optical storage media; flashmemory devices; electrical, optical or acoustical or any other type ofmedia suitable for storing information.

FIG. 9 depicts an example dynamic data platform system 900 fordetermining data dependency of dynamic tiles. In general, the dynamicdata platform system 900 may comprise a data field manager 910 forperforming the methods associated with determining data dependency asdisclosed herein.

As shown in FIG. 9, the data field manager 910 may comprise a datafields module 920, dependency module 930, and a data field update module940. In some embodiments, the data field manager 910 may receivedatabase data 950 and modification data 960. For example, the databasedata 950 may be information from one or more databases that has beenorganized into dynamic tiles as previously discussed. Furthermore, themodification data 960 may comprise a change to the database data 950after it has been received by the data field manager 910. In someembodiments, the data fields module 920 may store the database data 950and the dependency module 930 may determine the dependencies between thedata fields of the data fields module 920. Furthermore, the data fieldupdate module 940 may request an update to data from a database inresponse to the modification data 960. For example, the data fieldupdate module 940 may issue an output request 970 to one or moredatabases in response to the modification data 960.

What is claimed is:
 1. A method to dynamically update a data field, themethod comprising: receiving data from a plurality of databases;organizing the received data into a plurality of data fields, wherein afirst data field is associated with a single database of the pluralityof databases; receiving a modification to the first data field of theplurality of data fields; identifying, by a computer, a dependencybetween the first data field and other data fields of the plurality ofdata fields; and updating a second data field of the plurality of datafields based on the dependency between the first data field and theother data fields, wherein the second data field is updated if thesecond data field is dependent upon the first data field.
 2. The methodof claim 1, wherein the dependency between the first data field and theother data fields of the plurality of data fields comprises anindication that a modification to the first data field requires anupdating of at least one data field of the other data fields.
 3. Themethod of claim 1, further comprising: displaying a plurality of dynamictiles based on a user selection of a first entry, wherein a firstdynamic tile comprises at least one of the data fields and is associatedwith a first query; receiving a user selection of a second entry; andexecuting the first query associated with the first dynamic tile inresponse to the user selection.
 4. The method of claim 3, wherein theexecution of the first query is performed without a user input of aquery, the method further comprising: displaying the first dynamic tilewith at least one updated data field in response to the execution of thefirst query, wherein the at least one updated data field is at leastpartly based on the user selection of the second entry.
 5. The method ofclaim 1, wherein the first data field is associated with a firstdatabase and the second data field is associated with a second database,the updating of the second data field results in the querying of thesecond database based on the modification of the first data field. 6.The method of claim 5, wherein the first database and the seconddatabase are independent of each other such that the first database andthe second database are associated with different locations anddifferent administrators.
 7. The method of claim 1, wherein the methodis to facilitate an import or export compliance environment.
 8. Anon-transitory computer readable medium carrying one or moreinstructions to dynamically update a data field, wherein the one or moreinstructions, when executed by one or more processors, causes the one ormore processors to perform the steps of: receiving data from a pluralityof databases; organizing the received data into a plurality of datafields, wherein a first data field is associated with a single databaseof the plurality of databases; receiving a modification to the firstdata field of the plurality of data fields; identifying a dependencybetween the first data field and other data fields of the plurality ofdata fields; and updating a second data field of the plurality of datafields based on the dependency between the first data field and theother data fields, wherein the second data field is updated if thesecond data field is dependent upon the first data field.
 9. Thenon-transitory computer readable medium of claim 8, wherein thedependency between the first data field and the other data fields of theplurality of data fields comprises an indication that a modification tothe first data field requires an updating of at least one data field ofthe other data fields.
 10. The non-transitory computer readable mediumof claim 8, wherein the steps further comprise: displaying a pluralityof dynamic tiles based on a user selection of a first entry, wherein afirst dynamic tile comprises at least one of the data fields and isassociated with a first query; receiving a user selection of a secondentry; and executing the first query associated with the first dynamictile in response to the user selection.
 11. The non-transitory computerreadable medium of claim 10, wherein the execution of the first query isperformed without a user input of a query, the steps further comprise:displaying the first dynamic tile with at least one updated data fieldin response to the execution of the first query, wherein the at leastone updated data field is at least partly based on the user selection ofthe second entry.
 12. The non-transitory computer readable medium ofclaim 8, wherein the first data field is associated with a firstdatabase and the second data field is associated with a second database,the updating of the second data field results in the querying of thesecond database based on the modification of the first data field. 13.The non-transitory computer readable medium of claim 12, wherein thefirst database and the second database are independent of each othersuch that the first database and the second database are associated withdifferent locations and different administrators.
 14. The non-transitorycomputer readable medium of claim 8, wherein the steps are to facilitatean import or export compliance environment.
 15. A system, comprising atleast one processor and memory, to dynamically update a data field, thesystem comprising: a module to receive data from a plurality ofdatabases; a module to organize the received data into a plurality ofdata fields, wherein a first data field is associated with a singledatabase of the plurality of databases; a module to receive amodification to the first data field of the plurality of data fields; amodule to identify a dependency between the first data field and otherdata fields of the plurality of data fields; and a module to update asecond data field of the plurality of data fields based on thedependency between the first data field and the other data fields,wherein the second data field is updated if the second data field isdependent upon the first data field.
 16. The system of claim 15, whereinthe dependency between the first data field and the other data fields ofthe plurality of data fields comprises an indication that a modificationto the first data field requires an updating of at least one data fieldof the other data fields.
 17. The system of claim 15, furthercomprising: a module to display a plurality of dynamic tiles based on auser selection of a first entry, wherein a first dynamic tile comprisesat least one of the data fields and is associated with a first query; amodule to receive a user selection of a second entry; and a module toexecute the first query associated with the first dynamic tile inresponse to the user selection.
 18. The system of claim 17, wherein theexecution of the first query is performed without a user input of aquery, the system further comprises: a module to display the firstdynamic tile with at least one updated data field in response to theexecution of the first query, wherein the at least one updated datafield is at least partly based on the user selection of the secondentry.
 19. The system of claim 15, wherein the first data field isassociated with a first database and the second data field is associatedwith a second database, the updating of the second data field results inthe querying of the second database based on the modification of thefirst data field.
 20. The system of claim 19, wherein the first databaseand the second database are independent of each other such that thefirst database and the second database are associated with differentlocations and different administrators.